Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb32ee20805acd03daf3d46a279630e1261d0bd37309203785c1ec62ff951c31

Tx prefix hash: 69d08ab39cb3b5b5e07d184cb803c7ebee3449bf4544a44fdb5d9fe3ca88cb46
Tx public key: dbf7f2aa80ec48b59ff54672c730659775a38a23b00bddef04db05ef5235d5a9
Timestamp: 1718137610 Timestamp [UCT]: 2024-06-11 20:26:50 Age [y:d:h:m:s]: 00:337:23:13:28
Block: 1042115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241549 RingCT/type: yes/0
Extra: 01dbf7f2aa80ec48b59ff54672c730659775a38a23b00bddef04db05ef5235d5a9021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb3849bda9cba8ef8a99a7b5f5aa1ef0978ceb903cbc07f211dcf9063aa18745 0.600000000000 1510954 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": 1042125, "vin": [ { "gen": { "height": 1042115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb3849bda9cba8ef8a99a7b5f5aa1ef0978ceb903cbc07f211dcf9063aa18745" } } ], "extra": [ 1, 219, 247, 242, 170, 128, 236, 72, 181, 159, 245, 70, 114, 199, 48, 101, 151, 117, 163, 138, 35, 176, 11, 221, 239, 4, 219, 5, 239, 82, 53, 213, 169, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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