Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3db2beed92a39c1a501da7783545641410294faf126233b47ac5dbee2ccfeb5

Tx prefix hash: 8b7e96442ff7d00f4d9249c3eef5fc983fdbb04653e09bbcc72e0d6d2b9fa140
Tx public key: 851301d9e70e3264769915228995f1b13b5986a0fea68f28d7e4be22d9fb3600
Timestamp: 1716384138 Timestamp [UCT]: 2024-05-22 13:22:18 Age [y:d:h:m:s]: 00:300:22:17:49
Block: 1027586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215090 RingCT/type: yes/0
Extra: 01851301d9e70e3264769915228995f1b13b5986a0fea68f28d7e4be22d9fb360002110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f47b80b5f89c50aea1ec07fc9adb30f65fe84cc8e7732d2d61fd949e180d424 0.600000000000 1495281 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": 1027596, "vin": [ { "gen": { "height": 1027586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f47b80b5f89c50aea1ec07fc9adb30f65fe84cc8e7732d2d61fd949e180d424" } } ], "extra": [ 1, 133, 19, 1, 217, 231, 14, 50, 100, 118, 153, 21, 34, 137, 149, 241, 177, 59, 89, 134, 160, 254, 166, 143, 40, 215, 228, 190, 34, 217, 251, 54, 0, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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