Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b935b9f2b63df6999290c2cf0ca5175bab7efc6d943e152f2eeeb6f3da90b032

Tx prefix hash: 739f501dfcdfdcfc0c55811953e473d91099931b4a1d2c157047d757116e9416
Tx public key: 891c50a9b5951fa9e24e7ba705216b8e64f6511affe840f0f08fe61fe086fb38
Timestamp: 1736799935 Timestamp [UCT]: 2025-01-13 20:25:35 Age [y:d:h:m:s]: 00:311:01:24:43
Block: 1196687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219825 RingCT/type: yes/0
Extra: 01891c50a9b5951fa9e24e7ba705216b8e64f6511affe840f0f08fe61fe086fb380211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d46ab27cdb1eb641197d713f9e0e51e1fe5b5aef26f4d54e1c8984b36c82ee9a 0.600000000000 1683288 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": 1196697, "vin": [ { "gen": { "height": 1196687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d46ab27cdb1eb641197d713f9e0e51e1fe5b5aef26f4d54e1c8984b36c82ee9a" } } ], "extra": [ 1, 137, 28, 80, 169, 181, 149, 31, 169, 226, 78, 123, 167, 5, 33, 107, 142, 100, 246, 81, 26, 255, 232, 64, 240, 240, 143, 230, 31, 224, 134, 251, 56, 2, 17, 0, 0, 0, 4, 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