Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 503fdf68380de7548ccdb476e3e90635c122da5c8a48b67fc589b3cf81bd1568

Tx prefix hash: 6552ee6cbbbd46b7eafd38ee3848e2014db1b3b394b6c092f1f26e398cf3e4b0
Tx public key: 36614393a17ffaf3106ee58de53a8da74efcc91726cb776e4f5cdfb8f88176e6
Timestamp: 1575765895 Timestamp [UCT]: 2019-12-08 00:44:55 Age [y:d:h:m:s]: 05:032:00:21:40
Block: 22554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1169266 RingCT/type: yes/0
Extra: 0136614393a17ffaf3106ee58de53a8da74efcc91726cb776e4f5cdfb8f88176e6020d3930303100020000000bcf3cb0

1 output(s) for total of 516.737653300000 dcy

stealth address amount amount idx
00: 35f31a7418af434252ec46fdc101eaef3f06b32dca8f7a36246bdfc094ef70b3 516.737653300000 35929 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": 22564, "vin": [ { "gen": { "height": 22554 } } ], "vout": [ { "amount": 516737653300, "target": { "key": "35f31a7418af434252ec46fdc101eaef3f06b32dca8f7a36246bdfc094ef70b3" } } ], "extra": [ 1, 54, 97, 67, 147, 161, 127, 250, 243, 16, 110, 229, 141, 229, 58, 141, 167, 78, 252, 201, 23, 38, 203, 119, 110, 79, 92, 223, 184, 248, 129, 118, 230, 2, 13, 57, 48, 48, 49, 0, 2, 0, 0, 0, 11, 207, 60, 176 ], "rct_signatures": { "type": 0 } }


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