Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbfdd7a08387536c11f5ce20c2d0677bcda3434e3ffc378f95b9e96f4f10b08d

Tx prefix hash: 68c04bb47a285f4c0cd2ff06bdb1a5b2a8b22b59fa080bb1d07585fb034e0e71
Tx public key: ef817411817342acbed83fdaa0d744621119af1720c9673df5dcc06ed7c76b6d
Timestamp: 1702247310 Timestamp [UCT]: 2023-12-10 22:28:30 Age [y:d:h:m:s]: 01:036:18:11:49
Block: 910378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287619 RingCT/type: yes/0
Extra: 01ef817411817342acbed83fdaa0d744621119af1720c9673df5dcc06ed7c76b6d02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2aac29976b3186b56a401a2feff8ec3551bc05962d95a2071389c333d1b0def 0.600000000000 1367529 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": 910388, "vin": [ { "gen": { "height": 910378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2aac29976b3186b56a401a2feff8ec3551bc05962d95a2071389c333d1b0def" } } ], "extra": [ 1, 239, 129, 116, 17, 129, 115, 66, 172, 190, 216, 63, 218, 160, 215, 68, 98, 17, 25, 175, 23, 32, 201, 103, 61, 245, 220, 192, 110, 215, 199, 107, 109, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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