Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f55d3d124fc7d1fda3227cf4cb779a078169d5d122b5284439932e504a15c417

Tx prefix hash: 660ed92567d5642cb882054609b463283bc2e312be85ef3a22c190f2becd0929
Tx public key: f08311a4174abf7f0073736796a5b5b6b0f6c978ce854038df68fb91898379fe
Timestamp: 1704609490 Timestamp [UCT]: 2024-01-07 06:38:10 Age [y:d:h:m:s]: 01:018:06:32:22
Block: 929935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274370 RingCT/type: yes/0
Extra: 01f08311a4174abf7f0073736796a5b5b6b0f6c978ce854038df68fb91898379fe02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4ab3848f77955d040103d7b8c9c0e857bf151f2065fe0ce74a83f2c67095212 0.600000000000 1387813 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": 929945, "vin": [ { "gen": { "height": 929935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4ab3848f77955d040103d7b8c9c0e857bf151f2065fe0ce74a83f2c67095212" } } ], "extra": [ 1, 240, 131, 17, 164, 23, 74, 191, 127, 0, 115, 115, 103, 150, 165, 181, 182, 176, 246, 201, 120, 206, 133, 64, 56, 223, 104, 251, 145, 137, 131, 121, 254, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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