Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25a1f691fbb4543cea7b2620573bc28206d241c61c672e12bd0a87b33580d834

Tx prefix hash: ea682cfb85082d439dfa8e0f96eb4e15da52319f744c93a5c2c53d22daf8d606
Tx public key: 914c958aed271d5750948c7364c2808bb83dbf39767a8d7e4413708a8d6a7f77
Timestamp: 1708402061 Timestamp [UCT]: 2024-02-20 04:07:41 Age [y:d:h:m:s]: 01:086:19:19:41
Block: 961400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323090 RingCT/type: yes/0
Extra: 01914c958aed271d5750948c7364c2808bb83dbf39767a8d7e4413708a8d6a7f7702110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 867f472ce9471f9c94b2cff31745afec2b92fb8193b2f5c3a8c2f37ed55b36ac 0.600000000000 1421009 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": 961410, "vin": [ { "gen": { "height": 961400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "867f472ce9471f9c94b2cff31745afec2b92fb8193b2f5c3a8c2f37ed55b36ac" } } ], "extra": [ 1, 145, 76, 149, 138, 237, 39, 29, 87, 80, 148, 140, 115, 100, 194, 128, 139, 184, 61, 191, 57, 118, 122, 141, 126, 68, 19, 112, 138, 141, 106, 127, 119, 2, 17, 0, 0, 0, 14, 0, 17, 5, 91, 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