Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fe00c00ba72e8f035a5d20deb8e72684ee792136bc95cbf0a96b7d760de9919

Tx prefix hash: 744ae76d573c5acd0e988133b4e15b6fc85518da29c54b10f0fe89dc03f05367
Tx public key: 7d50a13c50f8562387221a4d8b7e72b1b47a1cfe45702cbd84e75a1a74ae6662
Timestamp: 1629214415 Timestamp [UCT]: 2021-08-17 15:33:35 Age [y:d:h:m:s]: 04:075:18:06:46
Block: 316019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1085830 RingCT/type: yes/0
Extra: 017d50a13c50f8562387221a4d8b7e72b1b47a1cfe45702cbd84e75a1a74ae6662021100000021282c04e2000000000000000000

1 output(s) for total of 55.068837075000 dcy

stealth address amount amount idx
00: 302f0a3235a10fbab8d807ba749bab4d40da7774c76545696925b8f60f103e12 55.068837075000 657556 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": 316029, "vin": [ { "gen": { "height": 316019 } } ], "vout": [ { "amount": 55068837075, "target": { "key": "302f0a3235a10fbab8d807ba749bab4d40da7774c76545696925b8f60f103e12" } } ], "extra": [ 1, 125, 80, 161, 60, 80, 248, 86, 35, 135, 34, 26, 77, 139, 126, 114, 177, 180, 122, 28, 254, 69, 112, 44, 189, 132, 231, 90, 26, 116, 174, 102, 98, 2, 17, 0, 0, 0, 33, 40, 44, 4, 226, 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