Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4978273cc0fede163d7a85b608882093b9d9b4efecf1ef531fb5c7a9b42b295f

Tx prefix hash: 6cd09f883e87853c504e94bd74eb3296843ba40f9c8e69e00f032f6ae24714f2
Tx public key: 50eacf14e3967f5b7760d077767f2a49c1b0bdb490639842ab54ffdcfd0b9de7
Timestamp: 1695575120 Timestamp [UCT]: 2023-09-24 17:05:20 Age [y:d:h:m:s]: 01:120:22:30:28
Block: 855254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347689 RingCT/type: yes/0
Extra: 0150eacf14e3967f5b7760d077767f2a49c1b0bdb490639842ab54ffdcfd0b9de7021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.899888111000 dcy

stealth address amount amount idx
00: 3cc1e0a2d24bb984cdbda0b5b4cdf25226098fe8218b207182c0fd6e558e5b97 0.899888111000 1309266 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": 855264, "vin": [ { "gen": { "height": 855254 } } ], "vout": [ { "amount": 899888111, "target": { "key": "3cc1e0a2d24bb984cdbda0b5b4cdf25226098fe8218b207182c0fd6e558e5b97" } } ], "extra": [ 1, 80, 234, 207, 20, 227, 150, 127, 91, 119, 96, 208, 119, 118, 127, 42, 73, 193, 176, 189, 180, 144, 99, 152, 66, 171, 84, 255, 220, 253, 11, 157, 231, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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