Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf493f13e4235b092373d59032b41f95638d07a1be71a44f6c2b77ed04b00a21

Tx prefix hash: e27498d8845fdb34bef87bcbac4d44909cebdbd8f4f983d14237131dfe45ecca
Tx public key: 001c7d0c38207b0f5ae4f276e4663933d32585bbd41b8ec80fbc6fb20dbbb254
Timestamp: 1709801131 Timestamp [UCT]: 2024-03-07 08:45:31 Age [y:d:h:m:s]: 01:265:06:25:06
Block: 973009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448330 RingCT/type: yes/0
Extra: 01001c7d0c38207b0f5ae4f276e4663933d32585bbd41b8ec80fbc6fb20dbbb25402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01169fd5aed25fd830db10f7fec5dd54d0b111cdce1f716fcdeb065d0aca1ece 0.600000000000 1432938 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": 973019, "vin": [ { "gen": { "height": 973009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01169fd5aed25fd830db10f7fec5dd54d0b111cdce1f716fcdeb065d0aca1ece" } } ], "extra": [ 1, 0, 28, 125, 12, 56, 32, 123, 15, 90, 228, 242, 118, 228, 102, 57, 51, 211, 37, 133, 187, 212, 27, 142, 200, 15, 188, 111, 178, 13, 187, 178, 84, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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