Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9740efe4ae0eb41f00bbfbe0436e19eb31195284013efac3bbfc577682b207f

Tx prefix hash: 1773fd36edf38522c33b7db0a6f534a5d374ed07b5d8e94014899040701e6bef
Tx public key: 454fd4407b0373b16c850cf5cfe270b61f2fa6fd83a6bdbbdc1a07ffb88e1055
Timestamp: 1739190212 Timestamp [UCT]: 2025-02-10 12:23:32 Age [y:d:h:m:s]: 00:321:15:58:17
Block: 1216212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227705 RingCT/type: yes/0
Extra: 01454fd4407b0373b16c850cf5cfe270b61f2fa6fd83a6bdbbdc1a07ffb88e1055021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fad5ce6afcc25ce27aad293ef5b13b1ae060d3d7c33cc5ef9f3f004b035d1e9 0.600000000000 1703015 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": 1216222, "vin": [ { "gen": { "height": 1216212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fad5ce6afcc25ce27aad293ef5b13b1ae060d3d7c33cc5ef9f3f004b035d1e9" } } ], "extra": [ 1, 69, 79, 212, 64, 123, 3, 115, 177, 108, 133, 12, 245, 207, 226, 112, 182, 31, 47, 166, 253, 131, 166, 189, 187, 220, 26, 7, 255, 184, 142, 16, 85, 2, 17, 0, 0, 0, 3, 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