Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e68478323181a8ba6d3e902e99cbfc4d9aaf95f3d72e32bc702af825907237a

Tx prefix hash: 501da0399fb3dba0f0b07987f80273a2ef551c1492017b09ea99e15b2e1c372c
Tx public key: 5a6fc4a40a688c98c236282f1a0dad7695483bd4ac01e865e7849e9fa7cef220
Timestamp: 1718156920 Timestamp [UCT]: 2024-06-12 01:48:40 Age [y:d:h:m:s]: 00:283:22:34:34
Block: 1042279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202906 RingCT/type: yes/0
Extra: 015a6fc4a40a688c98c236282f1a0dad7695483bd4ac01e865e7849e9fa7cef22002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e22bf4c439e0a9e2edb7aab4873d8b0ecf2a84d918edbcd164f4c40b31b68aa 0.600000000000 1511158 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": 1042289, "vin": [ { "gen": { "height": 1042279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e22bf4c439e0a9e2edb7aab4873d8b0ecf2a84d918edbcd164f4c40b31b68aa" } } ], "extra": [ 1, 90, 111, 196, 164, 10, 104, 140, 152, 194, 54, 40, 47, 26, 13, 173, 118, 149, 72, 59, 212, 172, 1, 232, 101, 231, 132, 158, 159, 167, 206, 242, 32, 2, 17, 0, 0, 0, 1, 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