Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ad21a2d44681cbe17f2755982bc5d50507f311db7302e4f447a97ae9c0b67d1

Tx prefix hash: 943540fce050cb2b008b5848e11c19b116e2c46db807b33091aefcc1ce3a14b1
Tx public key: 2980919dd6297e588b310f4f6db1b1c9062f8eadd31de17af9608b036767dbad
Timestamp: 1698373167 Timestamp [UCT]: 2023-10-27 02:19:27 Age [y:d:h:m:s]: 01:172:16:44:36
Block: 878470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384431 RingCT/type: yes/0
Extra: 012980919dd6297e588b310f4f6db1b1c9062f8eadd31de17af9608b036767dbad02110000000333af99f4000000000000000000

1 output(s) for total of 0.753814062000 dcy

stealth address amount amount idx
00: 0f55905da2fa84b1ff3fc42d0d542a42e32d085dc876afb3df374a79b54d0103 0.753814062000 1333918 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": 878480, "vin": [ { "gen": { "height": 878470 } } ], "vout": [ { "amount": 753814062, "target": { "key": "0f55905da2fa84b1ff3fc42d0d542a42e32d085dc876afb3df374a79b54d0103" } } ], "extra": [ 1, 41, 128, 145, 157, 214, 41, 126, 88, 139, 49, 15, 79, 109, 177, 177, 201, 6, 47, 142, 173, 211, 29, 225, 122, 249, 96, 139, 3, 103, 103, 219, 173, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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