Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 564ea86adddce5fe92e445ba74d5b1bb134b86ee0b9780e98f901ed492b72497

Tx prefix hash: f87161d29626c60e2187c4025091e5d69eb0abe7cb0a2bb95df0086e49edfa38
Tx public key: 16f37aca6ed4120502a3f0b12b2ea169079a6ff874cba1d048c97c72572039a7
Timestamp: 1673010652 Timestamp [UCT]: 2023-01-06 13:10:52 Age [y:d:h:m:s]: 01:330:19:27:54
Block: 668846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497452 RingCT/type: yes/0
Extra: 0116f37aca6ed4120502a3f0b12b2ea169079a6ff874cba1d048c97c72572039a702110000000552542ceb000000000000000000

1 output(s) for total of 3.731088150000 dcy

stealth address amount amount idx
00: f8d2e6f869d1c651aad642d6b518cb3c66cc8eb5dcd82fb968a17731b2f08eb6 3.731088150000 1110115 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": 668856, "vin": [ { "gen": { "height": 668846 } } ], "vout": [ { "amount": 3731088150, "target": { "key": "f8d2e6f869d1c651aad642d6b518cb3c66cc8eb5dcd82fb968a17731b2f08eb6" } } ], "extra": [ 1, 22, 243, 122, 202, 110, 212, 18, 5, 2, 163, 240, 177, 43, 46, 161, 105, 7, 154, 111, 248, 116, 203, 161, 208, 72, 201, 124, 114, 87, 32, 57, 167, 2, 17, 0, 0, 0, 5, 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