Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd4f513ef5a81973b9e0e9f1074bd99e2dedb53441c21d62e5314106213dfac4

Tx prefix hash: 0a899cfcacdfc869231f4843ba43cfd1f52208c296a4ffec3be771dfc75eff46
Tx public key: f361796606adbea27cbaedc9b51d1d9dd9d006eadd98544c21b81e1562e446fb
Timestamp: 1701583585 Timestamp [UCT]: 2023-12-03 06:06:25 Age [y:d:h:m:s]: 01:128:16:14:04
Block: 904870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353117 RingCT/type: yes/0
Extra: 01f361796606adbea27cbaedc9b51d1d9dd9d006eadd98544c21b81e1562e446fb02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.616296976000 dcy

stealth address amount amount idx
00: 5127cfba69b5e046efe55a2254f9dd7834677e7ec1ae79c25e51b8c5286d47d7 0.616296976000 1361653 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": 904880, "vin": [ { "gen": { "height": 904870 } } ], "vout": [ { "amount": 616296976, "target": { "key": "5127cfba69b5e046efe55a2254f9dd7834677e7ec1ae79c25e51b8c5286d47d7" } } ], "extra": [ 1, 243, 97, 121, 102, 6, 173, 190, 162, 124, 186, 237, 201, 181, 29, 29, 157, 217, 208, 6, 234, 221, 152, 84, 76, 33, 184, 30, 21, 98, 228, 70, 251, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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