Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87091fc65b91fd9f5a52d65df7b15902b5b5b4fd117d6c2faef33bb0dc60c1be

Tx prefix hash: a6f4b109a9b199d1c0b861f21a690f3187bcaf836e639eabb7f0999ebd7ed33b
Tx public key: 0d817f0246bf36d2b0b943bacd77343c3193d621fc0e2738b32392f31cfab343
Timestamp: 1734726648 Timestamp [UCT]: 2024-12-20 20:30:48 Age [y:d:h:m:s]: 00:086:06:17:53
Block: 1179557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61417 RingCT/type: yes/0
Extra: 010d817f0246bf36d2b0b943bacd77343c3193d621fc0e2738b32392f31cfab3430211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 291da089f7188a8c13ffbfbd913d51af6db85cdce6f40360c60bc11691358725 0.600000000000 1665952 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": 1179567, "vin": [ { "gen": { "height": 1179557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "291da089f7188a8c13ffbfbd913d51af6db85cdce6f40360c60bc11691358725" } } ], "extra": [ 1, 13, 129, 127, 2, 70, 191, 54, 210, 176, 185, 67, 186, 205, 119, 52, 60, 49, 147, 214, 33, 252, 14, 39, 56, 179, 35, 146, 243, 28, 250, 179, 67, 2, 17, 0, 0, 0, 6, 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