Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 107180bfc82f9087d895994488df14cbcbd9719a68dc1b0b781ad2a6b3a89627

Tx prefix hash: a76e5dc9611ae933f446c69e14d2a54df55c636b48ea857a2ea85b89e6b53b4e
Tx public key: 065dfe5afabdc6b977a0b8ca8deb00d8946e8d80971d914bc0bbf731c0c0d1b0
Timestamp: 1730435508 Timestamp [UCT]: 2024-11-01 04:31:48 Age [y:d:h:m:s]: 00:081:20:47:21
Block: 1143984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58534 RingCT/type: yes/0
Extra: 01065dfe5afabdc6b977a0b8ca8deb00d8946e8d80971d914bc0bbf731c0c0d1b00211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 010ac56d9210373d2b54fa46d78c95381dfac89a5458d09edc9910fa3a779c78 0.600000000000 1628039 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": 1143994, "vin": [ { "gen": { "height": 1143984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "010ac56d9210373d2b54fa46d78c95381dfac89a5458d09edc9910fa3a779c78" } } ], "extra": [ 1, 6, 93, 254, 90, 250, 189, 198, 185, 119, 160, 184, 202, 141, 235, 0, 216, 148, 110, 141, 128, 151, 29, 145, 75, 192, 187, 247, 49, 192, 192, 209, 176, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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