Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4737df3eac8d62ca19b3cd2f511eba58abd43193a4bfe1e887d09df2402d2c86

Tx prefix hash: 3825adffbb30f42a23c93b47b57cb28134d69872db00955dfe240ad0fed3ef49
Tx public key: d5d6b3cbfa345fa7a7f291e23aa77b366e0117d12c3ff47bee03d2ffd209cf6e
Timestamp: 1718622200 Timestamp [UCT]: 2024-06-17 11:03:20 Age [y:d:h:m:s]: 00:290:14:43:17
Block: 1046137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207657 RingCT/type: yes/0
Extra: 01d5d6b3cbfa345fa7a7f291e23aa77b366e0117d12c3ff47bee03d2ffd209cf6e02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06b6f79a4243087ac1aaa74f00e237eb8008044971cd428a25e2e923770a8971 0.600000000000 1515908 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": 1046147, "vin": [ { "gen": { "height": 1046137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06b6f79a4243087ac1aaa74f00e237eb8008044971cd428a25e2e923770a8971" } } ], "extra": [ 1, 213, 214, 179, 203, 250, 52, 95, 167, 167, 242, 145, 226, 58, 167, 123, 54, 110, 1, 23, 209, 44, 63, 244, 123, 238, 3, 210, 255, 210, 9, 207, 110, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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