Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb60a6c03b48e677795cd62fc8132c73f02c242c3e1377292c497fb003b3c1c6

Tx prefix hash: ddd5c0454981f49bb1cf67c71355d341adafdd9c1cbbcf4d59fb4881efd4c883
Tx public key: 89b36d0512929a4a042f3c93cc0ddf9b0e143a63e103fa3f6d273827ca530680
Timestamp: 1730727428 Timestamp [UCT]: 2024-11-04 13:37:08 Age [y:d:h:m:s]: 00:076:20:59:55
Block: 1146400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54957 RingCT/type: yes/0
Extra: 0189b36d0512929a4a042f3c93cc0ddf9b0e143a63e103fa3f6d273827ca5306800211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa0f9c5e63cb3f84e1ff696ad27741d969ab18cd2e2358b4f800609525ed048b 0.600000000000 1631041 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": 1146410, "vin": [ { "gen": { "height": 1146400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa0f9c5e63cb3f84e1ff696ad27741d969ab18cd2e2358b4f800609525ed048b" } } ], "extra": [ 1, 137, 179, 109, 5, 18, 146, 154, 74, 4, 47, 60, 147, 204, 13, 223, 155, 14, 20, 58, 99, 225, 3, 250, 63, 109, 39, 56, 39, 202, 83, 6, 128, 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