Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe5291e48673e46b916045a86cb1c2e04efa97403713d93c05e576b3fab9ca15

Tx prefix hash: 652b031d3e48f3fc1f751ba4b0019cafd72222510d9a9cc7f2d1d05ce2c3b7eb
Tx public key: 10ef7438ba6cb8b2781fb8bc201576ffa5a77ca067a27edff7971351407741bb
Timestamp: 1731074677 Timestamp [UCT]: 2024-11-08 14:04:37 Age [y:d:h:m:s]: 01:012:21:58:48
Block: 1149289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267645 RingCT/type: yes/0
Extra: 0110ef7438ba6cb8b2781fb8bc201576ffa5a77ca067a27edff7971351407741bb0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff0c5882b0cc133ab2b29514281ae43fbf0d9a2790f3c4a5f76a0d45f0339135 0.600000000000 1634334 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": 1149299, "vin": [ { "gen": { "height": 1149289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff0c5882b0cc133ab2b29514281ae43fbf0d9a2790f3c4a5f76a0d45f0339135" } } ], "extra": [ 1, 16, 239, 116, 56, 186, 108, 184, 178, 120, 31, 184, 188, 32, 21, 118, 255, 165, 167, 124, 160, 103, 162, 126, 223, 247, 151, 19, 81, 64, 119, 65, 187, 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