Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1b2b570e55b0f9a422c1c35302a4f86f6f71318b62ba7e49371938795e6b422

Tx prefix hash: 66c39db0901e190e5ac187f32cc04ec66fc711223b8f2b111d248e279fc2b873
Tx public key: e146883f193c027579d0b2af6aec37cfb646ef5b45c073100a3bd3c98ee02815
Timestamp: 1732691102 Timestamp [UCT]: 2024-11-27 07:05:02 Age [y:d:h:m:s]: 00:117:13:24:06
Block: 1162672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83815 RingCT/type: yes/0
Extra: 01e146883f193c027579d0b2af6aec37cfb646ef5b45c073100a3bd3c98ee02815021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a6b7bc754818b00d368c5c2016de01c5b6b822abd7baa38297267593ab79a42 0.600000000000 1648329 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": 1162682, "vin": [ { "gen": { "height": 1162672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a6b7bc754818b00d368c5c2016de01c5b6b822abd7baa38297267593ab79a42" } } ], "extra": [ 1, 225, 70, 136, 63, 25, 60, 2, 117, 121, 208, 178, 175, 106, 236, 55, 207, 182, 70, 239, 91, 69, 192, 115, 16, 10, 59, 211, 201, 142, 224, 40, 21, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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