Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0934a2c029559405e1932c715e97cd9bd5711976e089c0a4b13562c4aa7feae5

Tx prefix hash: 989695e8913bc78794ddd702aa4472c7a7b20db958055400b845d296c0d0f2f4
Tx public key: 5a8db1538f6f1c44e5aff59a53e90f7d0e6f237de38056e12b7a90cbe4986d8a
Timestamp: 1736104765 Timestamp [UCT]: 2025-01-05 19:19:25 Age [y:d:h:m:s]: 00:097:01:53:54
Block: 1190936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69162 RingCT/type: yes/0
Extra: 015a8db1538f6f1c44e5aff59a53e90f7d0e6f237de38056e12b7a90cbe4986d8a02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1132c2354b6a64465cfdb522b5d3e62bffc2e6c1f103f35b00bb43ad8e34f0a1 0.600000000000 1677459 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": 1190946, "vin": [ { "gen": { "height": 1190936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1132c2354b6a64465cfdb522b5d3e62bffc2e6c1f103f35b00bb43ad8e34f0a1" } } ], "extra": [ 1, 90, 141, 177, 83, 143, 111, 28, 68, 229, 175, 245, 154, 83, 233, 15, 125, 14, 111, 35, 125, 227, 128, 86, 225, 43, 122, 144, 203, 228, 152, 109, 138, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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