Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4ab781a5d00f536bc2408537357817f551a7ca384e450b869742f0d5e23cb31

Tx prefix hash: 2b4528f0da791438465a9c4ea3549f0b6ad3d0e39a0f423eb15d2e0094c77ef9
Tx public key: d8615256c8d59bdcb83b7e1691d269706a6135146a10d4696460622a67d3a7ad
Timestamp: 1714775887 Timestamp [UCT]: 2024-05-03 22:38:07 Age [y:d:h:m:s]: 00:249:13:46:15
Block: 1014254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178626 RingCT/type: yes/0
Extra: 01d8615256c8d59bdcb83b7e1691d269706a6135146a10d4696460622a67d3a7ad0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49664650a4fcf29d8a1d4c02df9dcc7caa0df841fb4d1078ff3278d6ec2ec702 0.600000000000 1477287 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": 1014264, "vin": [ { "gen": { "height": 1014254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49664650a4fcf29d8a1d4c02df9dcc7caa0df841fb4d1078ff3278d6ec2ec702" } } ], "extra": [ 1, 216, 97, 82, 86, 200, 213, 155, 220, 184, 59, 126, 22, 145, 210, 105, 112, 106, 97, 53, 20, 106, 16, 212, 105, 100, 96, 98, 42, 103, 211, 167, 173, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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