Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd98ddf4129f3d9a226ede0402effd5e724420e17f0cdfa46a4f3bbd2d65fbdb

Tx prefix hash: 7afaff0df64fdc650d442337275ec73aed4baaef814e579d2b0d44ffed54ca1a
Tx public key: c08e5d81003fec339aa4d9b5220ea84524d9f876b18af102f67108a000393780
Timestamp: 1716395011 Timestamp [UCT]: 2024-05-22 16:23:31 Age [y:d:h:m:s]: 01:170:19:41:36
Block: 1027664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380690 RingCT/type: yes/0
Extra: 01c08e5d81003fec339aa4d9b5220ea84524d9f876b18af102f67108a0003937800211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f0bd0fb2c9ed94f591e5720d49b04e43359e8cf4f01d8faf662c90536d4e1a5 0.600000000000 1495407 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": 1027674, "vin": [ { "gen": { "height": 1027664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f0bd0fb2c9ed94f591e5720d49b04e43359e8cf4f01d8faf662c90536d4e1a5" } } ], "extra": [ 1, 192, 142, 93, 129, 0, 63, 236, 51, 154, 164, 217, 181, 34, 14, 168, 69, 36, 217, 248, 118, 177, 138, 241, 2, 246, 113, 8, 160, 0, 57, 55, 128, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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