Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb2ebab0fdd8e1d21882774b855fa61ed40a7cd3e5fa69d653eff4089f0f5497

Tx prefix hash: 04a11e6e654dd8a39195eb8930f61412051470ef4e07e4aa2d973e0f9e05c7b5
Tx public key: c42377da2b7b3eb0bc698f1ff899fca9875351a32918bdf793b0cec94d5f3ae3
Timestamp: 1702010638 Timestamp [UCT]: 2023-12-08 04:43:58 Age [y:d:h:m:s]: 00:343:03:59:25
Block: 908406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245722 RingCT/type: yes/0
Extra: 01c42377da2b7b3eb0bc698f1ff899fca9875351a32918bdf793b0cec94d5f3ae3021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5b39b22600219bf0886482565b1f492d135819fdb8e6fc405e53daa13080713 0.600000000000 1365439 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": 908416, "vin": [ { "gen": { "height": 908406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5b39b22600219bf0886482565b1f492d135819fdb8e6fc405e53daa13080713" } } ], "extra": [ 1, 196, 35, 119, 218, 43, 123, 62, 176, 188, 105, 143, 31, 248, 153, 252, 169, 135, 83, 81, 163, 41, 24, 189, 247, 147, 176, 206, 201, 77, 95, 58, 227, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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