Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eadf67e53edb1922438e4884c0224e1a3b56ffd6f535771b4d33404a594b043a

Tx prefix hash: fd01b46b371c28c858589f4f8ba2d00ea79a310ab8c484142af45ddae4b73310
Tx public key: d2e9cbe84bc72080af70a7a7bc79cb38820d7ce869bfc10e3ea1e10ec793364c
Timestamp: 1711712401 Timestamp [UCT]: 2024-03-29 11:40:01 Age [y:d:h:m:s]: 00:285:17:58:31
Block: 988872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204523 RingCT/type: yes/0
Extra: 01d2e9cbe84bc72080af70a7a7bc79cb38820d7ce869bfc10e3ea1e10ec793364c02110000001359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5758b977067e056cac7934099d7edb2997ba40ff02b50fde4130d7d8d6575b6b 0.600000000000 1449159 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": 988882, "vin": [ { "gen": { "height": 988872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5758b977067e056cac7934099d7edb2997ba40ff02b50fde4130d7d8d6575b6b" } } ], "extra": [ 1, 210, 233, 203, 232, 75, 199, 32, 128, 175, 112, 167, 167, 188, 121, 203, 56, 130, 13, 124, 232, 105, 191, 193, 14, 62, 161, 225, 14, 199, 147, 54, 76, 2, 17, 0, 0, 0, 19, 89, 218, 211, 245, 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