Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84bdec2d6f9ed480f20004abe7e3b2455ebde2a8d84a22d03e1ea98962618dfa

Tx prefix hash: ff05ee792fd7ff1e8d5c81def6bddfeb50ec99eb6aa19b55e19052b4752ff8de
Tx public key: 6e8a0773e5a18bcc3bf7780c1b525ad49f84e219786ee9169cc4093a254aa960
Timestamp: 1730726177 Timestamp [UCT]: 2024-11-04 13:16:17 Age [y:d:h:m:s]: 00:152:08:26:08
Block: 1146392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108719 RingCT/type: yes/0
Extra: 016e8a0773e5a18bcc3bf7780c1b525ad49f84e219786ee9169cc4093a254aa960021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1832120c7872f6a32d7e521c782c59479c045fb6a80645e79603d668e671204 0.600000000000 1631029 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": 1146402, "vin": [ { "gen": { "height": 1146392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1832120c7872f6a32d7e521c782c59479c045fb6a80645e79603d668e671204" } } ], "extra": [ 1, 110, 138, 7, 115, 229, 161, 139, 204, 59, 247, 120, 12, 27, 82, 90, 212, 159, 132, 226, 25, 120, 110, 233, 22, 156, 196, 9, 58, 37, 74, 169, 96, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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