Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7121c313d41aa17e5cc4d5ea024e179caed826445521b6357dd968d5e2471664

Tx prefix hash: 884ac23cff90c2bce84547ee0862252f8a53b1134f69b789f99a73327a87b346
Tx public key: 7f6a56c65b30baaabc22901dd8bd0b50698faedacb698cfe8655e36b7d3c0e07
Timestamp: 1699351809 Timestamp [UCT]: 2023-11-07 10:10:09 Age [y:d:h:m:s]: 01:163:00:21:31
Block: 886375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377710 RingCT/type: yes/0
Extra: 017f6a56c65b30baaabc22901dd8bd0b50698faedacb698cfe8655e36b7d3c0e0702110000000233af99f4000000000000000000

1 output(s) for total of 0.709694887000 dcy

stealth address amount amount idx
00: ffe408e8d2e5443ada63d62318800fc6fea0a79a6aab91f63cea2c6eb063c77b 0.709694887000 1342190 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 886385, "vin": [ { "gen": { "height": 886375 } } ], "vout": [ { "amount": 709694887, "target": { "key": "ffe408e8d2e5443ada63d62318800fc6fea0a79a6aab91f63cea2c6eb063c77b" } } ], "extra": [ 1, 127, 106, 86, 198, 91, 48, 186, 170, 188, 34, 144, 29, 216, 189, 11, 80, 105, 143, 174, 218, 203, 105, 140, 254, 134, 85, 227, 107, 125, 60, 14, 7, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8