Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 114b8b27e0e5f8e94db41119024ce3ad83a2c81827901d99f2de58ba22cb86ad

Tx prefix hash: 74baab48dd759a78a7c5709c9b9d8e505bd1b9e0710f9ba572cd21de77f01cee
Tx public key: 34ecce45457406c4d480c4cf24311e759f8162a0e32a3a4e332f92babc1759bb
Timestamp: 1723358293 Timestamp [UCT]: 2024-08-11 06:38:13 Age [y:d:h:m:s]: 01:091:13:07:29
Block: 1085395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323903 RingCT/type: yes/0
Extra: 0134ecce45457406c4d480c4cf24311e759f8162a0e32a3a4e332f92babc1759bb021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b936cce2811a5536f0a0d4eb16dfb56d0b3f594cd9137093af66b04727e00fa8 0.600000000000 1559968 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": 1085405, "vin": [ { "gen": { "height": 1085395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b936cce2811a5536f0a0d4eb16dfb56d0b3f594cd9137093af66b04727e00fa8" } } ], "extra": [ 1, 52, 236, 206, 69, 69, 116, 6, 196, 212, 128, 196, 207, 36, 49, 30, 117, 159, 129, 98, 160, 227, 42, 58, 78, 51, 47, 146, 186, 188, 23, 89, 187, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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