Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d4b3e281163ebabc5ff5757feb9c0b1ce447a16e24151113e3051a8f62a6e27

Tx prefix hash: 490d43596116acf278806ee4607eebf9d356494ede8b7b4fd9c9594f5e34a006
Tx public key: 1c7a5c7fe99bdad282f1e1e743ecb7be328ba0c2312224bab1129db23913ef34
Timestamp: 1680371134 Timestamp [UCT]: 2023-04-01 17:45:34 Age [y:d:h:m:s]: 02:005:10:28:55
Block: 729917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525389 RingCT/type: yes/0
Extra: 011c7a5c7fe99bdad282f1e1e743ecb7be328ba0c2312224bab1129db23913ef340211000000045029cbac000000000000000000

1 output(s) for total of 2.341435553000 dcy

stealth address amount amount idx
00: 63636841b7b59e500b85aa05cdd5c3716e498b3611beab0d258e47c6bd748d1f 2.341435553000 1175492 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": 729927, "vin": [ { "gen": { "height": 729917 } } ], "vout": [ { "amount": 2341435553, "target": { "key": "63636841b7b59e500b85aa05cdd5c3716e498b3611beab0d258e47c6bd748d1f" } } ], "extra": [ 1, 28, 122, 92, 127, 233, 155, 218, 210, 130, 241, 225, 231, 67, 236, 183, 190, 50, 139, 160, 194, 49, 34, 36, 186, 177, 18, 157, 178, 57, 19, 239, 52, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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