Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 041a092836a825ae31be14c35ebe42d49e9072602c89e873b5d5f81e5faacb06

Tx prefix hash: cf618ac72d594d2251fe02a788fd512176f5e135f76527c6fee7e48e62f5dc6a
Tx public key: f0cf2fcaaa1c958e17bc406c273b142860fef3ff8ecad91a060febf800c95044
Timestamp: 1730840805 Timestamp [UCT]: 2024-11-05 21:06:45 Age [y:d:h:m:s]: 00:137:02:52:47
Block: 1147333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97841 RingCT/type: yes/0
Extra: 01f0cf2fcaaa1c958e17bc406c273b142860fef3ff8ecad91a060febf800c950440211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26295ca953aded7aa98e5df7c3b10f8894ba97d1a10eef39b2a7050d1d4109b5 0.600000000000 1632028 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": 1147343, "vin": [ { "gen": { "height": 1147333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26295ca953aded7aa98e5df7c3b10f8894ba97d1a10eef39b2a7050d1d4109b5" } } ], "extra": [ 1, 240, 207, 47, 202, 170, 28, 149, 142, 23, 188, 64, 108, 39, 59, 20, 40, 96, 254, 243, 255, 142, 202, 217, 26, 6, 15, 235, 248, 0, 201, 80, 68, 2, 17, 0, 0, 0, 2, 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