Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab8608a0a1a63c6eeeb720591c4cc36941945a4a8f6ee02b57f9ae9b15033b6f

Tx prefix hash: adb9e0a087aaf01a99cc41df1a44e81858ff11a676a61230a75e16eed3843ddf
Tx public key: 981b9cd10c25cc960c7521ca2877943db09ab1c31de04df268f63fb73db90abd
Timestamp: 1730966119 Timestamp [UCT]: 2024-11-07 07:55:19 Age [y:d:h:m:s]: 00:151:18:43:46
Block: 1148385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108294 RingCT/type: yes/0
Extra: 01981b9cd10c25cc960c7521ca2877943db09ab1c31de04df268f63fb73db90abd0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29eb0ca0c6a96818a931e961df6b44f6adc043329652c1ac9e1c0e8e9f5a003e 0.600000000000 1633210 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": 1148395, "vin": [ { "gen": { "height": 1148385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29eb0ca0c6a96818a931e961df6b44f6adc043329652c1ac9e1c0e8e9f5a003e" } } ], "extra": [ 1, 152, 27, 156, 209, 12, 37, 204, 150, 12, 117, 33, 202, 40, 119, 148, 61, 176, 154, 177, 195, 29, 224, 77, 242, 104, 246, 63, 183, 61, 185, 10, 189, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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