Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49f0686be4abfe137d4229b57c809da809178455c186898d831c917145d33610

Tx prefix hash: a88b727a48834ab5a36d890c66edbbc6d925e38d6ed1d642f90c2244e2cd5b10
Tx public key: 50162e400e37d62069e5654baaea4b0ca0625e95b4e65f393ab029a6c6cee806
Timestamp: 1735708694 Timestamp [UCT]: 2025-01-01 05:18:14 Age [y:d:h:m:s]: 01:006:10:46:06
Block: 1187652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263074 RingCT/type: yes/0
Extra: 0150162e400e37d62069e5654baaea4b0ca0625e95b4e65f393ab029a6c6cee80602110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b36aea1854b5ed3414684e235c7d39c4d7920f39ed91390898ccd80a8373a431 0.600000000000 1674145 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": 1187662, "vin": [ { "gen": { "height": 1187652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b36aea1854b5ed3414684e235c7d39c4d7920f39ed91390898ccd80a8373a431" } } ], "extra": [ 1, 80, 22, 46, 64, 14, 55, 214, 32, 105, 229, 101, 75, 170, 234, 75, 12, 160, 98, 94, 149, 180, 230, 95, 57, 58, 176, 41, 166, 198, 206, 232, 6, 2, 17, 0, 0, 0, 15, 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