Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a130496787a1dc2a70888bc37837729600671bfcba7fe3363ca4c404a0c5b1c2

Tx prefix hash: d4e2bac7fb5e1ee9cf7c7a60a443b4e9d1fb01570438fb4f66b120eb528f0aef
Tx public key: d579f0a0e5f998e0ec0035d3f3dd66b034d782426ff8a139bdbf107ef754e2ec
Timestamp: 1658985577 Timestamp [UCT]: 2022-07-28 05:19:37 Age [y:d:h:m:s]: 02:236:15:13:27
Block: 553337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 690318 RingCT/type: yes/0
Extra: 01d579f0a0e5f998e0ec0035d3f3dd66b034d782426ff8a139bdbf107ef754e2ec0211000000026570b1ef000000000000000000

1 output(s) for total of 9.006684404000 dcy

stealth address amount amount idx
00: 0a64d029924acfbb47a4f0f675c46205fa58077e889257a51e77b097411a92e9 9.006684404000 985117 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": 553347, "vin": [ { "gen": { "height": 553337 } } ], "vout": [ { "amount": 9006684404, "target": { "key": "0a64d029924acfbb47a4f0f675c46205fa58077e889257a51e77b097411a92e9" } } ], "extra": [ 1, 213, 121, 240, 160, 229, 249, 152, 224, 236, 0, 53, 211, 243, 221, 102, 176, 52, 215, 130, 66, 111, 248, 161, 57, 189, 191, 16, 126, 247, 84, 226, 236, 2, 17, 0, 0, 0, 2, 101, 112, 177, 239, 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