Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31e28492b2eaed4307b2bbcdff1de749e2b840a320b2a49a688eba0564dee34d

Tx prefix hash: f8ef1735471d9372003955c1a67c8136c4ba741d9f644e5a694871b0da804609
Tx public key: 0c4133bdc5daa57f13631398875ea2922153fff8a3ff329b8a12b67a1be0b3c4
Timestamp: 1716048722 Timestamp [UCT]: 2024-05-18 16:12:02 Age [y:d:h:m:s]: 00:345:03:30:19
Block: 1024795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246717 RingCT/type: yes/0
Extra: 010c4133bdc5daa57f13631398875ea2922153fff8a3ff329b8a12b67a1be0b3c402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecdc4c229364cf528a73b3bbce5a115e581900a692c343565f6e32f85d10835e 0.600000000000 1490824 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": 1024805, "vin": [ { "gen": { "height": 1024795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecdc4c229364cf528a73b3bbce5a115e581900a692c343565f6e32f85d10835e" } } ], "extra": [ 1, 12, 65, 51, 189, 197, 218, 165, 127, 19, 99, 19, 152, 135, 94, 162, 146, 33, 83, 255, 248, 163, 255, 50, 155, 138, 18, 182, 122, 27, 224, 179, 196, 2, 17, 0, 0, 0, 3, 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