Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb2e64ec7cdba8c7da417ec9d84454140fe1db5a5336f050ac72acf4f6b2ce10

Tx prefix hash: 593d0f602e47a746ca637cd3e12a2d527b361bbed44c873e7846fae17caaca3a
Tx public key: fb8011cbda6ebf0fe95b04549ee299781efb1b865abebdcf35b0d272cf0a4321
Timestamp: 1728404040 Timestamp [UCT]: 2024-10-08 16:14:00 Age [y:d:h:m:s]: 00:157:15:53:23
Block: 1127227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112486 RingCT/type: yes/0
Extra: 01fb8011cbda6ebf0fe95b04549ee299781efb1b865abebdcf35b0d272cf0a4321021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e2c62d15d1de626ff996081aee6a73af52ae9c8755068c8fcb3e63a7eba474d 0.600000000000 1610028 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": 1127237, "vin": [ { "gen": { "height": 1127227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e2c62d15d1de626ff996081aee6a73af52ae9c8755068c8fcb3e63a7eba474d" } } ], "extra": [ 1, 251, 128, 17, 203, 218, 110, 191, 15, 233, 91, 4, 84, 158, 226, 153, 120, 30, 251, 27, 134, 90, 190, 189, 207, 53, 176, 210, 114, 207, 10, 67, 33, 2, 17, 0, 0, 0, 2, 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