Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24a298032dd3ee1ba0ae9948e9ed07809cf205d15a6475516c901c0fa5bdaa00

Tx prefix hash: 718691a5a01d56ea491b7e7b757292eda05c53cfe5770ee47d29d818e1e13721
Tx public key: 8aba586fe2c804f72a7d336dea51ff3053eab89689a5df98d24e44921979c0a0
Timestamp: 1724846757 Timestamp [UCT]: 2024-08-28 12:05:57 Age [y:d:h:m:s]: 00:294:00:20:10
Block: 1097735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209922 RingCT/type: yes/0
Extra: 018aba586fe2c804f72a7d336dea51ff3053eab89689a5df98d24e44921979c0a0021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54f620a44b2db0c5ab295b315cc975f532a0dbc3ab24677fd7ce97d1e4e3dfcc 0.600000000000 1573204 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": 1097745, "vin": [ { "gen": { "height": 1097735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54f620a44b2db0c5ab295b315cc975f532a0dbc3ab24677fd7ce97d1e4e3dfcc" } } ], "extra": [ 1, 138, 186, 88, 111, 226, 200, 4, 247, 42, 125, 51, 109, 234, 81, 255, 48, 83, 234, 184, 150, 137, 165, 223, 152, 210, 78, 68, 146, 25, 121, 192, 160, 2, 17, 0, 0, 0, 2, 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