Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e780e0a14aad5794b9090424c1814dbee717e905cc00aee41fe9a6df16580103

Tx prefix hash: 2752602b6658d1269ff68e71a0e7884082d6b6f72eca343a1afed95b6a8b468c
Tx public key: 3fd615bd423e2485b25e8040a9be7b7d591280927af3c6454cde445c1f082d46
Timestamp: 1713427711 Timestamp [UCT]: 2024-04-18 08:08:31 Age [y:d:h:m:s]: 01:043:13:06:50
Block: 1003046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292124 RingCT/type: yes/0
Extra: 013fd615bd423e2485b25e8040a9be7b7d591280927af3c6454cde445c1f082d460211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bbbd240ef2b794f36e3d4118ab3f7da261c08db15796d6d3b20aca72dce7d59 0.600000000000 1463576 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": 1003056, "vin": [ { "gen": { "height": 1003046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bbbd240ef2b794f36e3d4118ab3f7da261c08db15796d6d3b20aca72dce7d59" } } ], "extra": [ 1, 63, 214, 21, 189, 66, 62, 36, 133, 178, 94, 128, 64, 169, 190, 123, 125, 89, 18, 128, 146, 122, 243, 198, 69, 76, 222, 68, 92, 31, 8, 45, 70, 2, 17, 0, 0, 0, 1, 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