Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69f27b319ac216d28c4b521961b85238cd862287aaff855b07db55d307e06c57

Tx prefix hash: 996b9425d2583f342bc362c4676cf3e09bd99d88b92f6702beb26f07402621ed
Tx public key: 1452b13511c2efc7d078820e43a65236b07890adf50582a3c5b0f85ae4353606
Timestamp: 1696769858 Timestamp [UCT]: 2023-10-08 12:57:38 Age [y:d:h:m:s]: 01:178:10:27:45
Block: 865177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388556 RingCT/type: yes/0
Extra: 011452b13511c2efc7d078820e43a65236b07890adf50582a3c5b0f85ae4353606021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.834275483000 dcy

stealth address amount amount idx
00: bb6a8df2b18e6fc3b6d056ff106d605f66e1bf834a24988a5fad69590b8ab334 0.834275483000 1319703 of 0

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": 865187, "vin": [ { "gen": { "height": 865177 } } ], "vout": [ { "amount": 834275483, "target": { "key": "bb6a8df2b18e6fc3b6d056ff106d605f66e1bf834a24988a5fad69590b8ab334" } } ], "extra": [ 1, 20, 82, 177, 53, 17, 194, 239, 199, 208, 120, 130, 14, 67, 166, 82, 54, 176, 120, 144, 173, 245, 5, 130, 163, 197, 176, 248, 90, 228, 53, 54, 6, 2, 17, 0, 0, 0, 4, 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