Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f21a16c11edb706677f8309dbda66a45188253e7ba89c4299dc55757d8e3890

Tx prefix hash: 4f8b0eb3b4c0daf6d6bfeca7da1ca06346e0a5a95cfdfb2b2e6c84c3c2d5d7a5
Tx public key: 795970c3a6a484f8329240bf50f990f9480d447b62e7a569c07fae3a72b157c5
Timestamp: 1700755954 Timestamp [UCT]: 2023-11-23 16:12:34 Age [y:d:h:m:s]: 01:067:13:33:28
Block: 898022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309422 RingCT/type: yes/0
Extra: 01795970c3a6a484f8329240bf50f990f9480d447b62e7a569c07fae3a72b157c502110000000833af99f4000000000000000000

1 output(s) for total of 0.649352196000 dcy

stealth address amount amount idx
00: b7def4982dae969955a461d3945b44209b346bbca7d971a2987c7d6004506c77 0.649352196000 1354425 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": 898032, "vin": [ { "gen": { "height": 898022 } } ], "vout": [ { "amount": 649352196, "target": { "key": "b7def4982dae969955a461d3945b44209b346bbca7d971a2987c7d6004506c77" } } ], "extra": [ 1, 121, 89, 112, 195, 166, 164, 132, 248, 50, 146, 64, 191, 80, 249, 144, 249, 72, 13, 68, 123, 98, 231, 165, 105, 192, 127, 174, 58, 114, 177, 87, 197, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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