Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c338df01919f74f1b60dd1d55070b6176af4f9e4e12ad79e42612c14bcbe22b0

Tx prefix hash: 2129c967b10c0842a5fcea3f774176cc0c0cc8d62056663df91a342f2242a1e3
Tx public key: f8ee628cf64c6a7e404f646a38ce5138c01a72ac84cbaed4d43aa810ebcd0603
Timestamp: 1719926826 Timestamp [UCT]: 2024-07-02 13:27:06 Age [y:d:h:m:s]: 00:277:03:11:54
Block: 1056949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198015 RingCT/type: yes/0
Extra: 01f8ee628cf64c6a7e404f646a38ce5138c01a72ac84cbaed4d43aa810ebcd06030211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16c336101158e36bbcf39f4b9b4364ae8f99f02e4389aa683498ff13c13781a7 0.600000000000 1527378 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": 1056959, "vin": [ { "gen": { "height": 1056949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16c336101158e36bbcf39f4b9b4364ae8f99f02e4389aa683498ff13c13781a7" } } ], "extra": [ 1, 248, 238, 98, 140, 246, 76, 106, 126, 64, 79, 100, 106, 56, 206, 81, 56, 192, 26, 114, 172, 132, 203, 174, 212, 212, 58, 168, 16, 235, 205, 6, 3, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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