Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90352845591dc5fd4625d057937fa743a3712a5c441a07ed49f12bf14dbf8eaa

Tx prefix hash: ee22d3af8b5041e3c4ac2c55311796b9455be06965d605cd7bc6235cb0cd1a67
Tx public key: 6ebe23f343b677ce2b0119e1afb01e60ef70d5168fa2ed4a162949440fe77bde
Timestamp: 1698062791 Timestamp [UCT]: 2023-10-23 12:06:31 Age [y:d:h:m:s]: 01:237:00:51:44
Block: 875888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430363 RingCT/type: yes/0
Extra: 016ebe23f343b677ce2b0119e1afb01e60ef70d5168fa2ed4a162949440fe77bde0211000000014b8f5122000000000000000000

1 output(s) for total of 0.768810801000 dcy

stealth address amount amount idx
00: 9ca089aea26b4df8be6a0d79b32227220b2a3a40d5eefd373f2184ec81ed2e42 0.768810801000 1331182 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": 875898, "vin": [ { "gen": { "height": 875888 } } ], "vout": [ { "amount": 768810801, "target": { "key": "9ca089aea26b4df8be6a0d79b32227220b2a3a40d5eefd373f2184ec81ed2e42" } } ], "extra": [ 1, 110, 190, 35, 243, 67, 182, 119, 206, 43, 1, 25, 225, 175, 176, 30, 96, 239, 112, 213, 22, 143, 162, 237, 74, 22, 41, 73, 68, 15, 231, 123, 222, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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