Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bcdc760e964dbc1f5d218c1d464fe79042ee0705860b1eee6bfc7499d442ae4

Tx prefix hash: 63a8eb76b38f9677ae97884e32db4755735dc0df4a5fdcb88101464b7ead1e5b
Tx public key: ba1cf094a4226d0d4fca313548b0273a113065e3c6640ab5799677ece53ebc21
Timestamp: 1706388711 Timestamp [UCT]: 2024-01-27 20:51:51 Age [y:d:h:m:s]: 01:031:03:29:37
Block: 944683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283314 RingCT/type: yes/0
Extra: 01ba1cf094a4226d0d4fca313548b0273a113065e3c6640ab5799677ece53ebc2102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8c9b5a6e5f2a906404ba7ebe2dda9434cf5da761705b0c2bc96a6b00bee7059 0.600000000000 1402969 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": 944693, "vin": [ { "gen": { "height": 944683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8c9b5a6e5f2a906404ba7ebe2dda9434cf5da761705b0c2bc96a6b00bee7059" } } ], "extra": [ 1, 186, 28, 240, 148, 164, 34, 109, 13, 79, 202, 49, 53, 72, 176, 39, 58, 17, 48, 101, 227, 198, 100, 10, 181, 121, 150, 119, 236, 229, 62, 188, 33, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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