Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14f6123c740f4c7eb13bc5ce9719958d8f636ea5408ebbf3917eb376778b56d4

Tx prefix hash: eb5275c20a5f8e72a36cf19a38d0ca3a29f7994d508dc5f146637dceb0a968bc
Tx public key: 1ea223464bf348ef4e3e2da7c8a17050d9a71f62a03b5779cbb719008312fa17
Timestamp: 1710781470 Timestamp [UCT]: 2024-03-18 17:04:30 Age [y:d:h:m:s]: 01:030:07:46:55
Block: 981142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282637 RingCT/type: yes/0
Extra: 011ea223464bf348ef4e3e2da7c8a17050d9a71f62a03b5779cbb719008312fa1702110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d7977c665643a753ae0cefa7fc00b3aa12e54accd0777929061b65fc8164e53 0.600000000000 1441235 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": 981152, "vin": [ { "gen": { "height": 981142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d7977c665643a753ae0cefa7fc00b3aa12e54accd0777929061b65fc8164e53" } } ], "extra": [ 1, 30, 162, 35, 70, 75, 243, 72, 239, 78, 62, 45, 167, 200, 161, 112, 80, 217, 167, 31, 98, 160, 59, 87, 121, 203, 183, 25, 0, 131, 18, 250, 23, 2, 17, 0, 0, 0, 7, 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