Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b1e74d366946a12c667133c4b25d8973afe7e5982be0356eb764bedc15a2fe6

Tx prefix hash: 00c79f4117a90f250609ecf6996e05dcba1911debf6d0d6f56b4abd4c5fb3069
Tx public key: 6ebb4676f5e5eabe0c78fe6cafee785ec8607b08e3079c6f0e718d2a3ff8f4d2
Timestamp: 1704319924 Timestamp [UCT]: 2024-01-03 22:12:04 Age [y:d:h:m:s]: 01:159:06:39:15
Block: 927575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374952 RingCT/type: yes/0
Extra: 016ebb4676f5e5eabe0c78fe6cafee785ec8607b08e3079c6f0e718d2a3ff8f4d202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac2695a2251c4964297a68b1fdf85d152fb8c779933dd442eb1d83b2bed353ee 0.600000000000 1385411 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": 927585, "vin": [ { "gen": { "height": 927575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac2695a2251c4964297a68b1fdf85d152fb8c779933dd442eb1d83b2bed353ee" } } ], "extra": [ 1, 110, 187, 70, 118, 245, 229, 234, 190, 12, 120, 254, 108, 175, 238, 120, 94, 200, 96, 123, 8, 227, 7, 156, 111, 14, 113, 141, 42, 63, 248, 244, 210, 2, 17, 0, 0, 0, 2, 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