Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ca5b1ddea24c74d5d137fdab4c62a95b9c889d042b72bc7fbc22efd99e79a62

Tx prefix hash: f1fd6a1432fa235cd3aa5ff71c60aebf6570f0761fbd2490b1362e0a55dccd1d
Tx public key: d5fe7c574d649ddb0e242b1d585c0238c3ab9a6004dba113b0dd751b143648bf
Timestamp: 1706386560 Timestamp [UCT]: 2024-01-27 20:16:00 Age [y:d:h:m:s]: 01:028:15:08:30
Block: 944668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281518 RingCT/type: yes/0
Extra: 01d5fe7c574d649ddb0e242b1d585c0238c3ab9a6004dba113b0dd751b143648bf02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4b4fe2c8e932976563f9b1647765725273d7ed2aacab279975d960347b7b91e 0.600000000000 1402954 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": 944678, "vin": [ { "gen": { "height": 944668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4b4fe2c8e932976563f9b1647765725273d7ed2aacab279975d960347b7b91e" } } ], "extra": [ 1, 213, 254, 124, 87, 77, 100, 157, 219, 14, 36, 43, 29, 88, 92, 2, 56, 195, 171, 154, 96, 4, 219, 161, 19, 176, 221, 117, 27, 20, 54, 72, 191, 2, 17, 0, 0, 0, 5, 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