Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4da91d924b0d6da261e24ec82694c64b57782faa3766e3192dbb25ce5c05ebd

Tx prefix hash: 617cc2732cdd0779e74fe843ef07df0c96c9364cd24d765d8ca4a45efdf5c8eb
Tx public key: 427f36e1b92467ef0a63a12871f97a7d920d4b7bb3c9cb158a6bf346268ff781
Timestamp: 1712386794 Timestamp [UCT]: 2024-04-06 06:59:54 Age [y:d:h:m:s]: 00:364:09:03:26
Block: 994409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260535 RingCT/type: yes/0
Extra: 01427f36e1b92467ef0a63a12871f97a7d920d4b7bb3c9cb158a6bf346268ff78102110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a81187fd08f7748ce674cca3772ca7adabfbffa93dcd5f5d2ec940f1024f676 0.600000000000 1454811 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": 994419, "vin": [ { "gen": { "height": 994409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a81187fd08f7748ce674cca3772ca7adabfbffa93dcd5f5d2ec940f1024f676" } } ], "extra": [ 1, 66, 127, 54, 225, 185, 36, 103, 239, 10, 99, 161, 40, 113, 249, 122, 125, 146, 13, 75, 123, 179, 201, 203, 21, 138, 107, 243, 70, 38, 143, 247, 129, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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