Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 793445a2b541c96069e904776704f915ee8fc27120a7b109a4d262d5bb12d63f

Tx prefix hash: a60dddbee48cd875d99661bed293efc2b2c2bbbe622a2cc42183734bc75eb08b
Tx public key: d46ed849c7bc7e684cda4df90ccbe1f438c3f1a1e93e736182811d3883ae3abe
Timestamp: 1730501383 Timestamp [UCT]: 2024-11-01 22:49:43 Age [y:d:h:m:s]: 00:153:00:12:46
Block: 1144529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109186 RingCT/type: yes/0
Extra: 01d46ed849c7bc7e684cda4df90ccbe1f438c3f1a1e93e736182811d3883ae3abe0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a273b15f679913a63183f80a802f3d7516f0e0cafb3c25aeae158105bb200568 0.600000000000 1628770 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": 1144539, "vin": [ { "gen": { "height": 1144529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a273b15f679913a63183f80a802f3d7516f0e0cafb3c25aeae158105bb200568" } } ], "extra": [ 1, 212, 110, 216, 73, 199, 188, 126, 104, 76, 218, 77, 249, 12, 203, 225, 244, 56, 195, 241, 161, 233, 62, 115, 97, 130, 129, 29, 56, 131, 174, 58, 190, 2, 17, 0, 0, 0, 4, 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