Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5178b2007fc7aaaf8b1e37cbf71ecb5f3cfea8ca4643ba1eb2c597c9bd70bdb5

Tx prefix hash: de7d391115e6da13ec26a939348cf8fdc757c2704fcef3ffb49ef9428001e066
Tx public key: bd0219c84f0689c56e1dd1404e0b0e4e01621ca9d8a021c24400a8ea4dbc6438
Timestamp: 1703361315 Timestamp [UCT]: 2023-12-23 19:55:15 Age [y:d:h:m:s]: 01:110:09:35:54
Block: 919611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340022 RingCT/type: yes/0
Extra: 01bd0219c84f0689c56e1dd1404e0b0e4e01621ca9d8a021c24400a8ea4dbc64380211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f803396d0ea88b1402f7dbd124aaefa234f3973e62318ad24c95db0522119897 0.600000000000 1377287 of 15

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": 919621, "vin": [ { "gen": { "height": 919611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f803396d0ea88b1402f7dbd124aaefa234f3973e62318ad24c95db0522119897" } } ], "extra": [ 1, 189, 2, 25, 200, 79, 6, 137, 197, 110, 29, 209, 64, 78, 11, 14, 78, 1, 98, 28, 169, 216, 160, 33, 194, 68, 0, 168, 234, 77, 188, 100, 56, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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