Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28acb2acb8a416ceca450ea682c29c21f8b8bde88fdae8038fe363d453c309a1

Tx prefix hash: 037b12b0f1fccf45c80a7a0c2aa5d9c4c99e316be313e49356ca43327aa52cfa
Tx public key: ce7925f9169f78ad4ec14fba6c4ef976c88b104044da332607d938dfc2600d74
Timestamp: 1721731373 Timestamp [UCT]: 2024-07-23 10:42:53 Age [y:d:h:m:s]: 00:256:18:28:17
Block: 1071899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183434 RingCT/type: yes/0
Extra: 01ce7925f9169f78ad4ec14fba6c4ef976c88b104044da332607d938dfc2600d7402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a426cf1cf48b9cbb8c24e5f0d81cd4cb2b75ffffd73c53fce5ee95a8b6d04e1 0.600000000000 1544296 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": 1071909, "vin": [ { "gen": { "height": 1071899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a426cf1cf48b9cbb8c24e5f0d81cd4cb2b75ffffd73c53fce5ee95a8b6d04e1" } } ], "extra": [ 1, 206, 121, 37, 249, 22, 159, 120, 173, 78, 193, 79, 186, 108, 78, 249, 118, 200, 139, 16, 64, 68, 218, 51, 38, 7, 217, 56, 223, 194, 96, 13, 116, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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