Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dafaf922059822d619ad50c4d88fac36668b5aee610cc37414667ed2513a0ca

Tx prefix hash: b38b1f3e18b0a117700238b91473a2d7bbaed445f16a03735a35ff0f5e818a79
Tx public key: b47e3de58fc82f6f4f1cf530c85ee58765598475daa9bb95e5e7f342f92a2a3f
Timestamp: 1710803508 Timestamp [UCT]: 2024-03-18 23:11:48 Age [y:d:h:m:s]: 01:003:02:16:08
Block: 981326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263171 RingCT/type: yes/0
Extra: 01b47e3de58fc82f6f4f1cf530c85ee58765598475daa9bb95e5e7f342f92a2a3f0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76ccd8cd316f1de13c4f3e3b6d128720d84a2d1200b3897e49c3ce16c09687a9 0.600000000000 1441421 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": 981336, "vin": [ { "gen": { "height": 981326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76ccd8cd316f1de13c4f3e3b6d128720d84a2d1200b3897e49c3ce16c09687a9" } } ], "extra": [ 1, 180, 126, 61, 229, 143, 200, 47, 111, 79, 28, 245, 48, 200, 94, 229, 135, 101, 89, 132, 117, 218, 169, 187, 149, 229, 231, 243, 66, 249, 42, 42, 63, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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