Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a049d6523d5011aa63258e0b6533e77141eeccb7d0df947d3a4ac63e7561100

Tx prefix hash: f28362219775da22758ca12b2bd70ce1a804df02f7e9bcbc87484bb020612698
Tx public key: 66203a4fd0ea2ae4a9e5f764f3afef41f11ef994547a41ad55bf44e332ef4945
Timestamp: 1723539030 Timestamp [UCT]: 2024-08-13 08:50:30 Age [y:d:h:m:s]: 00:216:02:15:26
Block: 1086899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154331 RingCT/type: yes/0
Extra: 0166203a4fd0ea2ae4a9e5f764f3afef41f11ef994547a41ad55bf44e332ef494502110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 351c868a154865bbf57e3ea216b6037dcf372ac94824d0cbd74077cd7a3fc1ab 0.600000000000 1561498 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": 1086909, "vin": [ { "gen": { "height": 1086899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "351c868a154865bbf57e3ea216b6037dcf372ac94824d0cbd74077cd7a3fc1ab" } } ], "extra": [ 1, 102, 32, 58, 79, 208, 234, 42, 228, 169, 229, 247, 100, 243, 175, 239, 65, 241, 30, 249, 148, 84, 122, 65, 173, 85, 191, 68, 227, 50, 239, 73, 69, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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