Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5eaf96c4b3710c2629621c126c7cb31c7365daad9fa4c64d9b8d44206566789

Tx prefix hash: 7218a9e8918e1a1e5b0f2bed644be9cd96a88c2ff78d8f8d99951c1b98e322ab
Tx public key: 0b7abb3880cae6a091344b1cd115679429206552b001f7be87faab371b1ffcb2
Timestamp: 1698348844 Timestamp [UCT]: 2023-10-26 19:34:04 Age [y:d:h:m:s]: 01:143:08:09:41
Block: 878271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363442 RingCT/type: yes/0
Extra: 010b7abb3880cae6a091344b1cd115679429206552b001f7be87faab371b1ffcb202110000000179bda3be000000000000000000

1 output(s) for total of 0.754959413000 dcy

stealth address amount amount idx
00: 44c7cf727424e5abc1d07a5a42b27daf6d9134cc8b7cec0f08adf641ccd89d9f 0.754959413000 1333701 of 0

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": 878281, "vin": [ { "gen": { "height": 878271 } } ], "vout": [ { "amount": 754959413, "target": { "key": "44c7cf727424e5abc1d07a5a42b27daf6d9134cc8b7cec0f08adf641ccd89d9f" } } ], "extra": [ 1, 11, 122, 187, 56, 128, 202, 230, 160, 145, 52, 75, 28, 209, 21, 103, 148, 41, 32, 101, 82, 176, 1, 247, 190, 135, 250, 171, 55, 27, 31, 252, 178, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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