Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e74db614125b6d251cbfef7f83ca9459a61ab42a9c1ebe2fea7180199a3e9657

Tx prefix hash: 21e12d017c3cb00a7a950d5109626cd9a69a42cf68b346e6f6f8d4d904bb2601
Tx public key: 5b4ec0df11b33c299756744f48761872788674617b78f96dab1ffd317be522d0
Timestamp: 1720367102 Timestamp [UCT]: 2024-07-07 15:45:02 Age [y:d:h:m:s]: 00:275:19:55:34
Block: 1060594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197089 RingCT/type: yes/0
Extra: 015b4ec0df11b33c299756744f48761872788674617b78f96dab1ffd317be522d0021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b24910bb0f2abc414154be9d8c5ce61dfdba30ad3aa6a9e4f8541898672f8cdc 0.600000000000 1531079 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": 1060604, "vin": [ { "gen": { "height": 1060594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b24910bb0f2abc414154be9d8c5ce61dfdba30ad3aa6a9e4f8541898672f8cdc" } } ], "extra": [ 1, 91, 78, 192, 223, 17, 179, 60, 41, 151, 86, 116, 79, 72, 118, 24, 114, 120, 134, 116, 97, 123, 120, 249, 109, 171, 31, 253, 49, 123, 229, 34, 208, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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