Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 730f9761366f82c097c1f1396a051d6111b69954f4d4dc2ccec028cf0eaa56e9

Tx prefix hash: 96997694f015fe51ab214ebecadc573bb1f3d5f6edfdb059e6816e6843bfcd10
Tx public key: cf073266c98a73a6303fe3fe671970735bc3e1ac00f7fd7303fa9bf8431f25d4
Timestamp: 1735814213 Timestamp [UCT]: 2025-01-02 10:36:53 Age [y:d:h:m:s]: 00:323:01:12:00
Block: 1188534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228396 RingCT/type: yes/0
Extra: 01cf073266c98a73a6303fe3fe671970735bc3e1ac00f7fd7303fa9bf8431f25d402110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecf445fc95a1aa2970de66276d71774a6f72aea104c728468f8a01d4d6e7c47a 0.600000000000 1675035 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": 1188544, "vin": [ { "gen": { "height": 1188534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecf445fc95a1aa2970de66276d71774a6f72aea104c728468f8a01d4d6e7c47a" } } ], "extra": [ 1, 207, 7, 50, 102, 201, 138, 115, 166, 48, 63, 227, 254, 103, 25, 112, 115, 91, 195, 225, 172, 0, 247, 253, 115, 3, 250, 155, 248, 67, 31, 37, 212, 2, 17, 0, 0, 0, 13, 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