Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 068eaf0a034abc4d44e696c8a6f299d972310db85393ccfe553bc9347ca1aeb3

Tx prefix hash: 61415deafb2060f91b59343013f34bcea5a35a282d2e590dd9383072ce7fc3b3
Tx public key: a18299216b1aa2b75ef941e7649aeaf79035d1ffec0801dad545343875b1f68d
Timestamp: 1700433096 Timestamp [UCT]: 2023-11-19 22:31:36 Age [y:d:h:m:s]: 01:161:23:24:35
Block: 895337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376959 RingCT/type: yes/0
Extra: 01a18299216b1aa2b75ef941e7649aeaf79035d1ffec0801dad545343875b1f68d021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.662791358000 dcy

stealth address amount amount idx
00: b72a37daa3e4707a50dd400f9228e7c7d54569f3861c4fab7e288661ed088f0e 0.662791358000 1351568 of 0

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": 895347, "vin": [ { "gen": { "height": 895337 } } ], "vout": [ { "amount": 662791358, "target": { "key": "b72a37daa3e4707a50dd400f9228e7c7d54569f3861c4fab7e288661ed088f0e" } } ], "extra": [ 1, 161, 130, 153, 33, 107, 26, 162, 183, 94, 249, 65, 231, 100, 154, 234, 247, 144, 53, 209, 255, 236, 8, 1, 218, 213, 69, 52, 56, 117, 177, 246, 141, 2, 17, 0, 0, 0, 3, 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