Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2991956e237ce45f56a05082ca8284d6b2671c39689c0d55e618487c3960d35a

Tx prefix hash: 513973eb01d21ad56cc52c190bcc30e07607b8d8db131b8ffc227ed2325e868f
Tx public key: 0b67d8e823f85fa7ee9503b186c1b444e9310c39c2d63b74caa80492d259f519
Timestamp: 1679055793 Timestamp [UCT]: 2023-03-17 12:23:13 Age [y:d:h:m:s]: 02:073:18:27:32
Block: 719005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574315 RingCT/type: yes/0
Extra: 010b67d8e823f85fa7ee9503b186c1b444e9310c39c2d63b74caa80492d259f5190211000000035029cbac000000000000000000

1 output(s) for total of 2.544707368000 dcy

stealth address amount amount idx
00: d2c23349f38f9f59e6e2efe3a01b6ba3bcc547b7551f5da0c39473dfd232ccf3 2.544707368000 1163704 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": 719015, "vin": [ { "gen": { "height": 719005 } } ], "vout": [ { "amount": 2544707368, "target": { "key": "d2c23349f38f9f59e6e2efe3a01b6ba3bcc547b7551f5da0c39473dfd232ccf3" } } ], "extra": [ 1, 11, 103, 216, 232, 35, 248, 95, 167, 238, 149, 3, 177, 134, 193, 180, 68, 233, 49, 12, 57, 194, 214, 59, 116, 202, 168, 4, 146, 210, 89, 245, 25, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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