Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de14b30f9375d3f2a76de5d816adc016a538e51bc7ac814f2dcaf47bb18d9e53

Tx prefix hash: f71a08ea4beb8ac88719ede6112bf099fc627f3d080893c764fb64edc4e22fa4
Tx public key: 61d220983e6bffa3ad94e58637d917932728a1a5aee1ba7061e74613ba48528a
Timestamp: 1685845990 Timestamp [UCT]: 2023-06-04 02:33:10 Age [y:d:h:m:s]: 01:230:20:34:19
Block: 774647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426371 RingCT/type: yes/0
Extra: 0161d220983e6bffa3ad94e58637d917932728a1a5aee1ba7061e74613ba48528a021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.664458935000 dcy

stealth address amount amount idx
00: 0b77f082ac9093584f721453fcb4315ef9b20917c6ac542aebe2ebf12c41dd76 1.664458935000 1224132 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": 774657, "vin": [ { "gen": { "height": 774647 } } ], "vout": [ { "amount": 1664458935, "target": { "key": "0b77f082ac9093584f721453fcb4315ef9b20917c6ac542aebe2ebf12c41dd76" } } ], "extra": [ 1, 97, 210, 32, 152, 62, 107, 255, 163, 173, 148, 229, 134, 55, 217, 23, 147, 39, 40, 161, 165, 174, 225, 186, 112, 97, 231, 70, 19, 186, 72, 82, 138, 2, 17, 0, 0, 0, 2, 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