Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00d6e4fd446720647fb08496767e608bd15090a1a6ed3596be9786a82cb18a3f

Tx prefix hash: 014d005622b2cece3bde23ef92bea385a57b8b1126d2a689ad3a624e5bb2638a
Tx public key: a9b7f1e81a0d530f7b76fac4abd527c2abdf2b3032bc57b719ab325a5d29690b
Timestamp: 1673431925 Timestamp [UCT]: 2023-01-11 10:12:05 Age [y:d:h:m:s]: 02:125:14:35:28
Block: 672345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 611468 RingCT/type: yes/0
Extra: 01a9b7f1e81a0d530f7b76fac4abd527c2abdf2b3032bc57b719ab325a5d29690b02110000000252542ceb000000000000000000

1 output(s) for total of 3.632803147000 dcy

stealth address amount amount idx
00: df3bb9fddd0fa280eb841a7c3d42c82957f365c06c9816305e945c0dccd1e224 3.632803147000 1113874 of 0

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": 672355, "vin": [ { "gen": { "height": 672345 } } ], "vout": [ { "amount": 3632803147, "target": { "key": "df3bb9fddd0fa280eb841a7c3d42c82957f365c06c9816305e945c0dccd1e224" } } ], "extra": [ 1, 169, 183, 241, 232, 26, 13, 83, 15, 123, 118, 250, 196, 171, 213, 39, 194, 171, 223, 43, 48, 50, 188, 87, 183, 25, 171, 50, 90, 93, 41, 105, 11, 2, 17, 0, 0, 0, 2, 82, 84, 44, 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