Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d371bb2bef4afb9d3ef0e45003b70074a4792f1073a336294537e99939eef43

Tx prefix hash: 374f28049b502c6adda3d46f39369368816266f90a08bb532a12956fcb0685ac
Tx public key: 02bd4b12f07e816fae7ae320b4928f6cfdd5cb4b8dbe3f9f539f064f1501aa3f
Timestamp: 1702676145 Timestamp [UCT]: 2023-12-15 21:35:45 Age [y:d:h:m:s]: 01:123:00:38:03
Block: 913930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349068 RingCT/type: yes/0
Extra: 0102bd4b12f07e816fae7ae320b4928f6cfdd5cb4b8dbe3f9f539f064f1501aa3f021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81d0f007cb5383a6be8e999f0eab142481aaeed238b1541615ed63bad119d453 0.600000000000 1371210 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": 913940, "vin": [ { "gen": { "height": 913930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81d0f007cb5383a6be8e999f0eab142481aaeed238b1541615ed63bad119d453" } } ], "extra": [ 1, 2, 189, 75, 18, 240, 126, 129, 111, 174, 122, 227, 32, 180, 146, 143, 108, 253, 213, 203, 75, 141, 190, 63, 159, 83, 159, 6, 79, 21, 1, 170, 63, 2, 17, 0, 0, 0, 1, 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