Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 324acea029b088c73a90f6d811d9c33d5ec199fefe70a7d6d89a0e3990d736f6

Tx prefix hash: 008d61f254562d214b4ea6ed1a80a86e0616ce37412396337f14dce5cc5cf0f9
Tx public key: 93f85c234441b2aee9c5d61b80231059b066dc65f421d53cebb0f087ef01aff3
Timestamp: 1652281735 Timestamp [UCT]: 2022-05-11 15:08:55 Age [y:d:h:m:s]: 02:310:21:30:15
Block: 498785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742489 RingCT/type: yes/0
Extra: 0193f85c234441b2aee9c5d61b80231059b066dc65f421d53cebb0f087ef01aff302110000000b2e6b1fd5000000000000000000

1 output(s) for total of 13.655840852000 dcy

stealth address amount amount idx
00: 7d3b343ff79007c549c3b035e1853520745bc745bc403051ffb96a9d9cbe58e4 13.655840852000 923024 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": 498795, "vin": [ { "gen": { "height": 498785 } } ], "vout": [ { "amount": 13655840852, "target": { "key": "7d3b343ff79007c549c3b035e1853520745bc745bc403051ffb96a9d9cbe58e4" } } ], "extra": [ 1, 147, 248, 92, 35, 68, 65, 178, 174, 233, 197, 214, 27, 128, 35, 16, 89, 176, 102, 220, 101, 244, 33, 213, 60, 235, 176, 240, 135, 239, 1, 175, 243, 2, 17, 0, 0, 0, 11, 46, 107, 31, 213, 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