Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36eb7e74b3a9e5db11142cc031b2ea344fd2103bac03c2f975a80850b6ded149

Tx prefix hash: 8b1a33669f1974107ca8837bf1806e87e1a8926df46bf1eeffb55a0e1f6cb767
Tx public key: b0326755d5874531d74c27bb3e2cfc4090b91745a3773e4fdd3eacd2ed7d0e6e
Timestamp: 1725028515 Timestamp [UCT]: 2024-08-30 14:35:15 Age [y:d:h:m:s]: 00:230:15:28:57
Block: 1099233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164719 RingCT/type: yes/0
Extra: 01b0326755d5874531d74c27bb3e2cfc4090b91745a3773e4fdd3eacd2ed7d0e6e02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f499ea32c481bb4605867acd143f8ebfffdf3ced1856cdd8a3ccc712557190b5 0.600000000000 1575178 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": 1099243, "vin": [ { "gen": { "height": 1099233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f499ea32c481bb4605867acd143f8ebfffdf3ced1856cdd8a3ccc712557190b5" } } ], "extra": [ 1, 176, 50, 103, 85, 213, 135, 69, 49, 215, 76, 39, 187, 62, 44, 252, 64, 144, 185, 23, 69, 163, 119, 62, 79, 221, 62, 172, 210, 237, 125, 14, 110, 2, 17, 0, 0, 0, 8, 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