Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbcc613098a6c9ac550a5ce5232f1d357ee60ff7be360303e1cd936ccc8f185c

Tx prefix hash: 76662208688b5b91cb8b465004885bb8e078a37bea6112ad498e2ee732b12ed1
Tx public key: 5417164c9cbfbaea9aed3e75bf0adc9590d5df3ef5699e214fc046c3c983ec7c
Timestamp: 1730524225 Timestamp [UCT]: 2024-11-02 05:10:25 Age [y:d:h:m:s]: 00:022:01:42:33
Block: 1144720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15797 RingCT/type: yes/0
Extra: 015417164c9cbfbaea9aed3e75bf0adc9590d5df3ef5699e214fc046c3c983ec7c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec55b5d30bb78a57fd5689bb742e6dda937618c45f06e68a6c1f983ce92b456b 0.600000000000 1629007 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": 1144730, "vin": [ { "gen": { "height": 1144720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec55b5d30bb78a57fd5689bb742e6dda937618c45f06e68a6c1f983ce92b456b" } } ], "extra": [ 1, 84, 23, 22, 76, 156, 191, 186, 234, 154, 237, 62, 117, 191, 10, 220, 149, 144, 213, 223, 62, 245, 105, 158, 33, 79, 192, 70, 195, 201, 131, 236, 124, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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