Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7e6f860285d44a56e6d5fffb43fd36fe9b6659c11e63d5e24a373dc5882c2ce

Tx prefix hash: 017fbea6cc63969e14a0bcb866fec58c2b0003b0e8c16f35259cf0702a4b989e
Tx public key: 3146aa7fd2495e7b62bc470b6be855eaf58c5d202e7f07a0f51782e319b77179
Timestamp: 1706949570 Timestamp [UCT]: 2024-02-03 08:39:30 Age [y:d:h:m:s]: 01:063:08:03:20
Block: 949344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306327 RingCT/type: yes/0
Extra: 013146aa7fd2495e7b62bc470b6be855eaf58c5d202e7f07a0f51782e319b7717902110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 327a619cf1fa2af908ca418c2c59cf31bcc71ce7f32168e2ad671c71ca9bb712 0.600000000000 1407868 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": 949354, "vin": [ { "gen": { "height": 949344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "327a619cf1fa2af908ca418c2c59cf31bcc71ce7f32168e2ad671c71ca9bb712" } } ], "extra": [ 1, 49, 70, 170, 127, 210, 73, 94, 123, 98, 188, 71, 11, 107, 232, 85, 234, 245, 140, 93, 32, 46, 127, 7, 160, 245, 23, 130, 227, 25, 183, 113, 121, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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