Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7f1042342173d63f62c399da4bea4948c22b5a6417496afcc9f0f99c6ff0d7c

Tx prefix hash: 58a17278d6e7c9a2e191194b48c1748bb22f1a325352b0379f00c6c7fcf7e970
Tx public key: 1fe3930a968de0a07b7ac9f5e124415734b476767eb6a10d763d1899453017eb
Timestamp: 1737145033 Timestamp [UCT]: 2025-01-17 20:17:13 Age [y:d:h:m:s]: 00:152:02:46:32
Block: 1199547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108414 RingCT/type: yes/0
Extra: 011fe3930a968de0a07b7ac9f5e124415734b476767eb6a10d763d1899453017eb021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9edce6a77f53b2bc416105b6d2c1c93118e7c09b830e91a28885dd618af9ee9b 0.600000000000 1686178 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": 1199557, "vin": [ { "gen": { "height": 1199547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9edce6a77f53b2bc416105b6d2c1c93118e7c09b830e91a28885dd618af9ee9b" } } ], "extra": [ 1, 31, 227, 147, 10, 150, 141, 224, 160, 123, 122, 201, 245, 225, 36, 65, 87, 52, 180, 118, 118, 126, 182, 161, 13, 118, 61, 24, 153, 69, 48, 23, 235, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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